View logical blocks

Models Yard Models Yard Models view Actions Open Yard Editor Yard Editor view Actions Edit Logical Blocks Logical Blocks view

The Logical Blocks view lists the logical blocks defined for your yard in the yard text file. A logical block is a block of containers that is not slot-specific but is still a location where containers are grouped together. Logical blocks are also used to describe a general status of a group of containers. For example, both the apron and TIP are logical blocks. Logical blocks are similar to heaps. However, you cannot define allocation groups for logical blocks to which you plan containers. (With heaps, this is possible.) Also the name of logical blocks cannot contain dots and spaces, whereas these are allowed for heap blocks.

Many logical blocks also have specific functionality and behavior that is not available for heaps. For example, XPS deletes containers in the Gate Out logical block after a certain number of days (the number of days is controlled by a setting). Some logical blocks refer to areas such as Chassis or Ground. Others indicate the status of a container's location, such as in Went Out, or Truck in Progress.

You use the Logical Blocks view to add new logical blocks or edit existing logical blocks in the Logical Block form (on page 1). You can also clone an existing block. In this case, N4 carries over the characteristics of the logical block; you only need to enter a new name. If you use the default logical blocks created by N4, you need to review the block names in the Logical Block form. If the names of the blocks are not as per your site, edit the block names and then apply yard model changes (on page 1).

N4 writes any logical blocks you define to the #LOG BLOCKS section of the yard source file.

The following table explains several commonly used logical blocks. The names are listed as they appear in the Block Purpose list in the Logical Block form (on page 1).

Name

Code

Function

Default

Apron

BR

Used for containers known to be discharged, but that do not yet have a yard position. It can also be used as a temporary holding position for containers moving between the ship and the yard, or vice versa.

You can create multiple Apron blocks and use any of them to position the containers while performing vessel moves.

Yes

Equipment Control

EC

Used for containers that are planned to the yard via allocations.

Yes

Ground

GRND

Used for a yard area other than the apron to which containers are discharged without having a specific yard placement.

No

Chassis

CHSS

Used to indicate the placement of stowage on chassis for immediate departure from the yard.

No

Divorce

DVRC

Used for some N4 Gate flows. In version 3.1, most DVRC block functionality replaced by CITC block.

Yes

Hopper

HOPR

A container for bulk material such as grain, coal, rock, etc.

 

Truck-in-Progress

TIP

Used for containers on trucks that have cleared the inner gate.

Yes

Truck Queue

TQ

Used for containers on trucks that have cleared the outer gate transaction and are now en route to the inner gate.

Yes

Failed to Deck

FLD

Used for containers that cannot be planned to the yard.

Yes

Community

COM

Used for boxes that are in "town" but not yet inside the terminal.

Yes

Rail

RAMP

Used for containers on trains. You can have more than one rail logical block; for example, one for inbound and one for outbound.

Yes

Gate Out

OUT

This logical block labels containers as being delivered at the gate but have not yet been deleted by N4. The XPS client deletes containers in this logical block automatically two days after the delivery work instruction is deleted.

Yes

Flip

FLIP

Used for containers entering or exiting the yard that must be "flipped" onto an alternate chassis.

No

Chassis in Transit Code

CITC

Represents the location of all chassis or cassette objects that are currently attached to a truck.

In version 3.1, replaces DVRC and MNTC functionality.

 

Notes:

The default logical blocks are the minimum required logical blocks. If they are not defined in the Logical Blocks form, then when validating the yard model in the Validate yard model form, exporting a compiled yard file, or applying yard model changes, N4 creates any missing required logical blocks and assigns the default icon. For more information on the logical block icons, see Table of Logical block icons.

Logical blocks of type Lane are not supported; however, exchange lanes as stack blocks are supported.

To add a new logical block record:

Click .

To edit or delete a logical block record:

  1. In the list view, select the record(s) that you want to edit or delete.

  1. Do one of the following:

Depending upon the list view, when you double-click a record in the list view, Yard Editor displays either an inspector that displays more details for the selected record or a form that enables you to edit the record.

Table: Logical block columns

Short Label

Long Label

In Filter?

Sorting?

Purpose

Block Purpose

X

X

Code Chars

Code Chars

X

X

Icon Id

Icon Id

X

X

Life Cycle

Life Cycle State

X

X

Long Name

Long Name

X

X

Name

Name

X

X

 

 

 

Logical Blocks Columns

Short Label

Long Label

In Filter?

Sorting?

Purpose

Block Purpose

X

X

Code Chars

Code Chars

X

X

Icon Id

Icon Id

X

X

Life Cycle

Life Cycle State

X

X

Long Name

Long Name

X

X

Name

Name

X

X